Updating the JewelSuite Floating License Server license file
When you receive a renewed or replacement license file, you need to load it onto the license server. A license file update can be performed with minimal disruption. Users who already have a license checked out are not affected, unless you need to do a full stop and restart.
Reread vs. restart: The Reread License File button refreshes the license server live without disconnecting active users. Use this whenever possible. A full Stop and Start terminates all active checkouts and should only be used if Reread fails or if you are also changing port numbers.
- Copy the new license file to the server. Place it in the same folder as the existing license server files (for example,
C:\Licensing\JewelSuite\11.19.9.1\). -
If you previously configured custom port numbers, open the new license file in a text editor and apply the same ports:
- The
lmgrdport is on theSERVERline:SERVER hostname hostid port - The vendor daemon port is on the
DAEMONline:DAEMON joa path PORT=port
See About the JewelSuite licensing model for a full description of the license file format.
- The
-
Point lmtools to the new license file:
- Run lmtools.exe as Administrator.
- On the Config Services tab, select the JewelSuite license service from the Service Name dropdown.
- Use the Browse button next to Path to the license file to select the new license file.
- Click Save Service.
- On the Start/Stop/Reread tab, click Reread License File.
- Return to the Config Services tab and click View Log. Scroll to the bottom and verify the new features are listed without errors.
-
If lmtools reports an error after Reread, perform a full restart: on the Start/Stop/Reread tab, click Stop Server, wait a few seconds, then click Start Server. Check the log again after restarting.
A full restart disconnects all active license checkouts. Notify users before doing this if licenses are currently in use. - If the log shows an error that you cannot resolve, contact the support department at SoftwareSupport@bakerhughes.com and attach the log file. For common issues and their resolutions, see Troubleshooting license errors.